This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this document. The identifiers are specified in a CSV file with the following syntax:

<SymbolName>, <Identifier>, <NodeClass>

Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId.

The BrowsePath for an Instance Node is constructed by appending the BrowseName of the instance Node to the BrowseName for the containing instance or type. An underscore character is used to separate each BrowseName in the path. Let’s take for example, the <OPENSCSSIDClassPropertyDataType> ObjectType Node which has the <PropertyValue> Property. The Name for the <PropertyValue> InstanceDeclaration within the <type> declaration is: OPENSCSSIDClassPropertyDataType_PropertyValue.

The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/OPENSCS-SER/

Note that NamespaceURIs are NOT live URLs.

The CSV released with this version of the specification can be found here:

http://www.opcfoundation.org/UA/schemas/OPENSCS/1.0/NodeIds.csv

NOTE    The latest CSV that is compatible with this version of the specification can be found here:

http://www.opcfoundation.org/UA/schemas/OPENSCS/NodeIds.csv

A computer processible version of the complete Information Model defined in this document is also provided. It follows the XML Information Model schema syntax defined in OPC 10000-6.

The Information Model Schema released with this version of the document can be found here:

http://www.opcfoundation.org/UA/schemas/OPENSCS/1.0/Opc.Ua.OPENSCS.NodeSet2.xml

NOTE    The latest Information Model schema that is compatible with this version of the document can be found here:

http://www.opcfoundation.org/UA/schemas/OPENSCS/Opc.Ua.OPENSCS.NodeSet2.xml

OPC UA Method result Codes

The OPC UA Method Result codes, from OPC 10000-4, are copied in Table 95.

Table 95 – OPC UA Method Result Codes

Result Code	Description
Bad_MethodInvalid	See OPC 10000-4 for the description of this result code. (The method id does not refer to a method for the specified object.)
Bad_NotImplemented	See OPC 10000-4 for the description of this result code. (Requested operation is not implemented.)
Bad_NodeIdUnknown	See OPC 10000-4 for the description of this result code. (Used to indicate that the specified object is not valid)
Bad_ArgumentsMissing	See OPC 10000-4 for the description of this result code (The client did not specify all of the input arguments for the method.)
Bad_TooManyArguments	See OPC 10000-4 for the description of this result code (The client specified more input arguments than defined for the method.)
Bad_InvalidArgument	See OPC 10000-4 for the description of this result code. (Used to indicate in the operation level results that one or more of the input arguments are invalid. The inputArgumentResults contain the specific status code for each invalid argument.)
Bad_TypeMismatch	See OPC 10000-4 for the description of this result code. (Used to indicate that an input argument does not have the correct data type.)
Bad_OutOfRange	See OPC 10000-4 for the description of this result code. (Used to indicate that an input argument is outside the acceptable range.)
Bad_Timeout	See OPC 10000-4 for the description of this result code. (The operation timed out. – the server did not respond to the command)
Bad_InvalidState	See OPC 10000-4 for the description of this result code. (The operation cannot be completed because the object is closed, uninitialized or in some other invalid state.)

(Normative) EPCIS File Transfer Format

EPCIS documents shall conform with GS1's EPCIS and Core Business Vocabulary (CBV) standards (i.e., ISO/IEC 19987 and 19988, respectively).

Additional guidance is provided by GS1's global, cross-sector EPCIS and CBV Implementation Guideline, as well as by the pharmaceutical supply chain-specific, GS1 US implementation guideline, “Applying GS1 Standards for DSCSA and Traceability”.

In addition, the following rules apply to transferred files:

1. The transferred file shall use UTF-8 encoding.
2. GS1 based identifiers shall be expressed as EPC Pure Identity URI encodings, as specified in GS1's EPC Tag Data Standard (TDS), specifically:

SGTIN EPC URI for trade items

Example:

urn:epc:id:sgtin: 0614141.112345.000000000400

SSCC EPC URI for logistic units

SGLN EPC URI for read points and business locations

Non-GS1 identifiers (e.g. country or region-specific codes, or communication within Level 2 and Level 3 that use company specific identification) shall follow CBV provisions for:

“General Considerations for HTTP URLs as User Vocabulary elements”,

“HTTP URLs for Instance-level identification of objects” and

“HTTP URLs for Location identifiers”

which are normatively defined in the GS1 Core Business Vocabulary Standard, Chapter 8 User Vocabularies.

Example (non-GS1 instance-level object identifier:

https://MyCountryDomain.eu/ProductCode/obj/8675ABC556

Example (non-GS1 location identifier):

https://local.com/HEX/loc/3114257BF5A13B8790000000

1. All serialized identifiers (i.e., SGTIN and SSCC), including but not limited to those appearing in shipping and packing events, shall first have been captured in a commissioning event (i.e., an EPCIS Object Event with action "ADD", business_step "urn:epcglobal:cbv:bizstep:commissioning" and disposition "urn:epcglobal:cbv:bizstep:active".
2. Aggregation shall be used to capture the relationship between each serialized parent and its immediate children (i.e., an EPCIS Aggregation Event with action "ADD" and business_step "urn:epcglobal:cbv:bizstep:packing"); each additional (nested) level of packaging hierarchy (i.e., grandparents and great-grandparents of the lowest registered level) must be expressed in an additional, dedicated EPCIS Aggregation Event.
3. Each shipped unit shall always be identified as a logistic unit and captured by means of its SSCC upon dispatch (i.e. an EPCIS Object Event with action "OBSERVE", business step "shipping" and disposition "in_transit").
4. Each individual hierarchical level packed within this logistic unit shall have been captured in an earlier EPCIS Aggregation Event.
5. Each commissioning event shall include as many SGTINs as practical; common sense shall be leveraged in conjunction with dialogue between communicating partners to establish an agreed approach to managing file sizes.

The maximum number of SGTINs must be agreed between communicating partners during design or change management of a system and should be represented in the properties MaxEPCISObjectEventSIDs and MaxEPCISAggregationEvents of the OPENSCSEventManagerObjectType.

While timestamping of individual EPCs (i.e., in individual EPCIS events) is to be avoided to avoid unnecessary bloating of payload, the opposite extreme of including an entire batch run in one event might cause file size exceptions.

Strictly enforce GS1 EPCIS chronology sequence standard to be upheld for any single EPC, for example:

For any single EPC, the Commission time must be before the Aggregation time which must be before the Shipping time.

The Aggregation timer of bottles into a case must be before the Aggregation of the case into a pallet.

Any single EPC cannot share the same timestamp in 2 separate events.

When possible do not include custom EPCIS event extensions as they increase file size. Where extensions cannot be avoided, these shall be implemented in compliance with the EPCIS standard's extensibility mechanism, including but not limited to declaration of the applicable vendor/user namespace.

Bibliography

OPC 10000-2, OPC Unified Architecture - Part 2: Security Model

DOCPROPERTY Part2URL \* MERGEFORMAT http://www.opcfoundation.org/UA/Part2/

OPC 10000-8, OPC Unified Architecture - Part 8: Data Access

DOCPROPERTY Part8URL \* MERGEFORMAT http://www.opcfoundation.org/UA/Part8/

OPC 10000-9, OPC UA Specification: Part 9 – Alarms & Conditions

DOCPROPERTY Part9URL \* MERGEFORMAT http://www.opcfoundation.org/UA/Part9/

OPC 10000-10, OPC UA Specification: Part 10 - Programs

DOCPROPERTY Part10URL \* MERGEFORMAT http://www.opcfoundation.org/UA/Part10/

OPC 10000-11, OPC Unified Architecture - Part 11: Historical Access

DOCPROPERTY Part11URL \* MERGEFORMAT http://www.opcfoundation.org/UA/Part11/

OPC 10000-13, OPC Unified Architecture - Part 13: Aggregates

DOCPROPERTY Part13URL \* MERGEFORMAT http://www.opcfoundation.org/UA/Part13/